Skip to content

Conversation

@peter-mitrano-ar
Copy link
Contributor

Like #2924 but for rolling, as @fujitatomoya requested.

@peter-mitrano-ar peter-mitrano-ar force-pushed the rolling-callback-error-improve-warning branch from 1726b87 to 80974e1 Compare August 7, 2025 15:01
@peter-mitrano-ar peter-mitrano-ar force-pushed the rolling-callback-error-improve-warning branch from 80974e1 to 54a9c82 Compare August 7, 2025 15:03
Copy link
Collaborator

@fujitatomoya fujitatomoya left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm with green CI.

@fujitatomoya
Copy link
Collaborator

Pulls: #2927
Gist: https://gist.githubusercontent.com/fujitatomoya/4b45ece35c4c05b353d1f03b0c3c82f2/raw/0756c0928b0b9f5d7d812e5f15dcc8f5092200a7/ros2.repos
BUILD args: --packages-above-and-dependencies rclcpp_lifecycle
TEST args: --packages-above rclcpp_lifecycle
ROS Distro: rolling
Job: ci_launcher
ci_launcher ran: https://ci.ros2.org/job/ci_launcher/16681

  • Linux Build Status
  • Linux-aarch64 Build Status
  • Linux-rhel Build Status
  • Windows Build Status

@peter-mitrano-ar
Copy link
Contributor Author

I am looking into the failure

@peter-mitrano-ar
Copy link
Contributor Author

After making the initial fix it seems [rclcpp.TestExecutor.spin_all_fail_wait_set_clear](https://build.ros2.org/job/Rpr__rclcpp__ubuntu_noble_amd64/735/testReport/rclcpp/TestExecutor/spin_all_fail_wait_set_clear/) is the current failure, but it seems this test is not reliable, as jenkins show it failing recently:
image

@fujitatomoya should the test be re-run or ignored somehow?

@fujitatomoya
Copy link
Collaborator

  • Linux Build Status
  • Linux-aarch64 Build Status
  • Linux-rhel Build Status
  • Windows Build Status

@peter-mitrano-ar
Copy link
Contributor Author

Let me know if I can do anything else to help merge! Thank you for being so attentive to this small contribution :)

@jmachowinski jmachowinski merged commit 3767779 into ros2:rolling Aug 12, 2025
2 of 3 checks passed
@jmachowinski
Copy link
Collaborator

https://github.com/Mergifyio backport kilted jazzy

@mergify
Copy link
Contributor

mergify bot commented Aug 12, 2025

backport kilted jazzy

✅ Backports have been created

mergify bot pushed a commit that referenced this pull request Aug 12, 2025
…ps misleading (#2927)

* change misleading warning message, making it more correct and informative

Signed-off-by: Peter Mitrano (AR) <[email protected]>

* Fix compile error. Needed to also build rcl from source.

Signed-off-by: Peter Mitrano (AR) <[email protected]>

* explicitely initialize pointer as null, to adhere to best practice

Signed-off-by: Peter Mitrano (AR) <[email protected]>

---------

Signed-off-by: Peter Mitrano (AR) <[email protected]>
(cherry picked from commit 3767779)
mergify bot pushed a commit that referenced this pull request Aug 12, 2025
…ps misleading (#2927)

* change misleading warning message, making it more correct and informative

Signed-off-by: Peter Mitrano (AR) <[email protected]>

* Fix compile error. Needed to also build rcl from source.

Signed-off-by: Peter Mitrano (AR) <[email protected]>

* explicitely initialize pointer as null, to adhere to best practice

Signed-off-by: Peter Mitrano (AR) <[email protected]>

---------

Signed-off-by: Peter Mitrano (AR) <[email protected]>
(cherry picked from commit 3767779)
jmachowinski pushed a commit that referenced this pull request Aug 13, 2025
…ps misleading (#2927) (#2931)

* change misleading warning message, making it more correct and informative



* Fix compile error. Needed to also build rcl from source.



* explicitely initialize pointer as null, to adhere to best practice



---------


(cherry picked from commit 3767779)

Signed-off-by: Peter Mitrano (AR) <[email protected]>
Co-authored-by: Peter Mitrano (AR) <[email protected]>
jmachowinski pushed a commit that referenced this pull request Aug 19, 2025
…ps misleading (#2927) (#2932)

* change misleading warning message, making it more correct and informative



* Fix compile error. Needed to also build rcl from source.



* explicitely initialize pointer as null, to adhere to best practice



---------


(cherry picked from commit 3767779)

Signed-off-by: Peter Mitrano (AR) <[email protected]>
Co-authored-by: Peter Mitrano (AR) <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants